Post not yet marked as solved
I have the same issue... in the developer portal it says "CarPlay Audio (CarPlay framework)"... but inside the provisioning profile there is still the old entitlement "com.apple.developer.playable-content". I contacted Apple a few weeks ago asking for access to the new "com.apple.developer.carplay-audio" entitlement. But no reply from them yet. This long wait time is ridiculous for something that shouldn't take more than a minute for the one responsible. All I'm asking is be able to migrate my app from the deprecated playable content API to the new carplay framework... this shouldn't take weeks or months for them to reply.
Post marked as Apple Recommended
Same thing happened with my project. I believe that this is an intentional change by Apple to force developers to start distributing xcframeworks with support for arm64 simulators (M1 Macs). Fat binary frameworks don't work anymore because simulators and actual devices can have the same architecture. The proper solution is to repack the GoogleCast framework into xcframework. You can do this by splitting the fat binary into two using lipo (one for simulator and one for real devices). If you don't want to do this, you can enable "Validate workspace" in build settings. This will enable you to build your project and only output a warning.
Post not yet marked as solved
If the update is urgent, you can try disabling bitcode. I did this and processing finished within minutes... the previous bitcode build is still stuck processing.
In case anyone else is wondering how to do this.I managed to achieve what I wanted using resizable images. Images can have a dark/light appearance and can be used in iOS versions prior to 11. I had to mimic the UI elements using UIImageViews. The hardest par was getting the constraints for different size classes right.PS: I tried the UIImage approach before... but it only started working with the latest Xcode 11 beta 7.
Post not yet marked as solved
All I can say is that it works in our app (iPhone 6s, iOS 13 beta 8). But unfortunatelly I've got no idea why it isn't working in your app.
Post not yet marked as solved
I found out how to change the color of the focused UITabBarItem. What they do is create an UIImage from the bar item text and overlay the image over the selection indicator. The UIImageView is set to UIImageRenderingModeAlwaysTemplate... which means it uses the UITabBars tintColor. If you need your selected item text to be white, just set the UITabBar tintColor to white.Still no idea about the other question though...
Post not yet marked as solved
No... it seems that we'll have to change the app to work with the new behaviour.
